home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
xfdv201a.arc
/
FILEDOOR.NEW
< prev
next >
Wrap
Text File
|
1991-05-08
|
3KB
|
59 lines
Howdy,
You can't say that I told you so, but the first 2.01 version contained
a number of small bugs. This update is far from perfect but it fixes
a number of small (and big) problems:
- Bimodem would give an error sometimes. Only the users who didn't
follow my suggestion (not instruction, it should work, but it did
not) to put the full drive and path before the BIMODEM.COM entry,
were presented with a nice HELP-screen from Bimodem both LOCAL and
REMOTE. This is now fixed though I still suggest you to put the
drive and path in front of the filename to gain speed;
- All protocols would give various errors when tested local. FileDoor
will now display a screen with calling-information as a replacement
to the real call when tested local (e.g. DORINFO1.DEF contains COM0);
- GIF files (when wanted) were not seen as archives. The can be a big
discussion about a GIF being an archive or not, the fact remains that
it is a compressed file. GIF's will not give a reduction on the
credits anymore (I will make this configurable in the real 2.02);
- The non-destructive backspace is now replaced with a real combination
of backspace, space, backspace to emulate the destructive backspace;
- Fixed some coding. When a user selected Download, used Bimodem and
did only upload, FileDoor would not count the credits. This is fixed;
- Fixed a problem with PFILES.BBS. These were selectable files and are
now excluded from the selection-list;
- Fixed a problem where the upload exit(s) were not called when Bimodem
was selected with 'D'ownload or 'U'pload;
- Added a new option. Many users reported an error with files that were
in the download area but not in the FILES.BBS. FileDoor would select
them even if they were not in the FILES.BBS. This was an original
FileDoor 1.21 option but has now been changed. You can add the option:
HideFiles {seclevel}
In FileDoor.CFG. {seclevel] is optional. When not present, it is set
to 65535 by default. If present it must be between 0 and 65535. If
this option is active the following happens:
- If a file is in the area AND in the FILES.BBS then it is still
selectable (based on security, ratio, credits and so);
- If a file is in the area and NOT in the FILES.BBS, then FileDoor
will compare user-security against {seclevel}. If {seclevel} is
higher, the user is not able to select that file, if {seclevel}
is the same or lower, user can select the file.
At this moment, flags are not counted for, but 2.02 will implement
these if there is any request for it. This is a global option and
should be driven by the BBS's security. To say it plain, I will not
implement in a way that it can be different for each file-area.
2.02 will contain some new gadgets and will fix things more permanently
if needed.
Thanks, Rob